Selective Encryption Delineation

ABSTRACT

Decoding a partially encrypted data stream may include receiving and scanning the partially encrypted data stream. Scanning the partially encrypted data stream may include identifying an encrypted portion sentinel in the partially encrypted data stream subsequent to a first portion, identifying an encrypted portion in the partially encrypted data stream subsequent to the encrypted portion sentinel, and generating a decrypted data portion by decrypting the encrypted portion. Decrypting the encrypted portion may include identifying an encrypted data portion in the encrypted portion, the encrypted data portion omitting an end encrypted portion sentinel, decrypting the encrypted data portion, and identifying an end encrypted portion sentinel in the encrypted portion subsequent to the encrypted data portion. Decoding the partially encrypted data stream may include including the decrypted data portion in the decrypted output data stream, and outputting the decrypted output data stream to a client device in the second network domain.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application claims priority to U.S. Provisional Patent ApplicationNo. 62/240,232, filed on Oct. 12, 2015, which is herein incorporated byreference in its entirety.

TECHNICAL FIELD

The present disclosure is generally related to information technology,and in particular to computer-implemented methods, systems, andapparatuses to delineate encrypted portions of a selectively encrypteddata stream in an electronic computing and communication system.

BACKGROUND

An electronic computing and communication system may include one or morecommunicating and computing elements, which may, in the course ofcommunicating and computing, exchange messages including a mixture ofsensitive and insensitive data. Accordingly, a method and apparatus fordelineating encrypted portions of a selectively encrypted data streammay be advantageous.

SUMMARY

Disclosed herein are aspects of selective encryption delineation.

According to an implementation, a method is provided for decoding apartially encrypted data stream. Decoding a partially encrypted datastream may include receiving a partially encrypted data stream, andscanning the partially encrypted data stream. Scanning the partiallyencrypted data stream may include identifying a first portion of thepartially encrypted data stream, wherein the first portion omits anencrypted portion sentinel, including the first portion in a decryptedoutput data stream, identifying an encrypted portion sentinel in thepartially encrypted data stream subsequent to the first portion,identifying an encrypted portion in the partially encrypted data streamsubsequent to the encrypted portion sentinel, and generating a decrypteddata portion by decrypting the encrypted portion. Decrypting theencrypted portion may include identifying an encrypted data portion inthe encrypted portion, the encrypted data portion omitting an endencrypted portion sentinel, decrypting the encrypted data portion, andidentifying an end encrypted portion sentinel in the encrypted portionsubsequent to the encrypted data portion. Decoding the partiallyencrypted data stream may include including the decrypted data portionin the decrypted output data stream, and outputting the decrypted outputdata stream to a client device in the second network domain.

According to an implementation, a method is provided for delineatingencrypted portions of a selectively encrypted data stream. Delineatingencrypted portions of a selectively encrypted data stream may includegenerating a partially encrypted data stream, and outputting thepartially encrypted data stream. Generating the partially encrypted datastream may include identifying an unencrypted input data portion,including the first unencrypted input portion in the partially encrypteddata stream, identifying an encrypted input data portion, including anencrypted portion sentinel in the partially encrypted data streamsubsequent to the first unencrypted input portion, including theencrypted input data portion in the partially encrypted data streamsubsequent to the encrypted portion sentinel, and including an endencrypted portion sentinel in the partially encrypted data streamsubsequent to the encrypted input data portion.

According to an implementation, a non-transitory computer-readablestorage medium, comprising executable instructions that, when executedby a processor, facilitate performance of operations, comprisingselective encryption delineation is provided. Selective encryptiondelineation may include receiving, at an edge encryption proxy in afirst network domain, from a client device in the first network domain,a first request for information, which may indicate a remote server in asecond network domain, and transmitting a second request for theinformation to the remote server on behalf of the client. Selectiveencryption delineation may include, in response to transmitting thesecond request to the remote server, receiving, from the remote server,at the edge encryption proxy, a partially encrypted data stream,identifying a first portion of the partially encrypted data stream,wherein the first portion omits an encrypted portion sentinel, andincluding the first portion in a decrypted output data stream. Selectiveencryption delineation may include identifying an encrypted portionsentinel in the partially encrypted data stream subsequent to the firstportion, identifying an encrypted portion in the partially encrypteddata stream subsequent to the encrypted portion sentinel, and generatinga decrypted data portion by decrypting the encrypted portion. Decryptingthe encrypted portion may include identifying an encrypted data portionin the encrypted portion, the encrypted data portion omitting an endencrypted portion sentinel, generating a decrypted data portion bydecrypting the encrypted data portion, such that the decrypted dataportion includes at least a portion of the information, and identifyingan end encrypted portion sentinel in the encrypted portion subsequent tothe encrypted data portion. Selective encryption delineation may includeincluding the decrypted data portion in the decrypted output datastream, and outputting the decrypted output data stream to the clientdevice as a response to the first request.

These and other aspects of the present disclosure are disclosed in thefollowing detailed description of the embodiments, the appended claimsand the accompanying figures.

BRIEF DESCRIPTION OF THE DRAWINGS

The description herein makes reference to the accompanying drawingswherein like reference numerals refer to like parts throughout theseveral views, and wherein:

FIG. 1 is a schematic of an example of a cloud computing system inaccordance with this disclosure;

FIG. 2 is a block diagram of an example internal configuration of acomputing device in accordance with this disclosure;

FIG. 3 is a schematic of another example of a cloud computing system inaccordance with this disclosure;

FIG. 4 is a diagram of an example of encrypting data using selectiveencryption delineation in accordance with this disclosure;

FIG. 5 is a diagram of an example of decrypting partially encrypted datausing selective encryption delineation in accordance with thisdisclosure; and

FIG. 6 is a diagram of an example of managing data encrypted usingselective encryption delineation in accordance with this disclosure.

DETAILED DESCRIPTION

An electronic computing and communication system may include manyelements, such as computers, routers, switches, servers, and the like,in communication internally, within the electronic computing andcommunication system or network domain, and externally, with elementsoutside the electronic computing and communication system or networkdomain. The communications may include sensitive information. In orderto prevent unauthorized access to the sensitive information, thesensitive information may be encrypted. Thus, the communications mayinclude a mixture of unencrypted and encrypted data. Accordingly, themethods and apparatus disclosed herein may enable the low cost, lowlatency, inclusion and detection of encrypted portions in partiallyencrypted data streams.

In some embodiments, selective encryption delineation may allow forrapid decryption of partially encrypted data with low resourceutilization and complexity, and little or no latency. For simplicity andclarity, a communication that includes a mixture of unencrypted andencrypted data may be referred to herein as a partially, or selectively,encrypted string, a partially, or selectively, encrypted message, orpartially, or selectively, encrypted data.

The preceding overview is provided to enable a basic or generalunderstanding of various aspects of the non-limiting embodiments thatfollow and the accompanying drawings. This overview is not intended asan exhaustive or complete description. Instead, the purpose of thisoverview is to introduce some concepts of this disclosure as a preludeto the following more detailed descriptions of the various embodiments.

FIG. 1 is a diagram of an example of an electronic computing andcommunication system 100 in accordance with this disclosure. As usedherein, the term ‘electronic computing and communication system’, orvariations thereof, may be, or include, a distributed computing system,such as a client-server computing system, a cloud computing system, aclustered computing system, or the like.

An electronic computing and communication system 100 can includecustomers, such as customers 110 and 120. A customer may have clients,such as clients 112, 114 for customer 110 and clients 122, 124 forcustomer 120. A client 112/114/122/124 may be a computing system, whichmay include one or more computing devices, such as a mobile phone, atablet computer, a laptop computer, a notebook computer, a desktopcomputer, or any other computing device, or combination of computingdevices. In some embodiments, client be implemented as a single physicalunit, or a combination of physical units. In some embodiments, a singlephysical unit may include multiple clients. For example, a client112/114/122/124 may be an instance of an application or program runningon a customer device. Although two customers 110/120, each having twoclients 112/114/122/124, are shown in FIG. 1, an electronic computingand communication system may include any number of customers or clientsor may have a different configuration of customers or clients. Forexample, there may be hundreds or thousands of customers and eachcustomer may have any number of clients. Although not shown separatelyin FIG. 1, a customer 110/120 may include a customer network or domain.For example, the clients 112/114 of a customer 110, may be within acustomer network or domain.

The electronic computing and communication system 100 can include one ormore datacenters, such as the two datacenters 130/140 shown. Adatacenter may include servers, such as the two servers 132/134 shownfor datacenter 130, or the two servers 142/144 shown for bottomdatacenter 140. A datacenter 130/140 may represent a geographiclocation, which may include a facility, where servers are located. Aserver 132/134/142/144 may be a computing system, which may include oneor more computing devices, such as a desktop computer, a servercomputer, or any other computer capable of operating as a server.Although two datacenters 130/140, each including two servers132/134/142/144 are shown in FIG. 1, an electronic computing andcommunication system may have any number of datacenters and servers ormay have a different configuration of datacenters and servers. Forexample, there may be tens of data centers and each data center may havehundreds or any number of servers. Although not shown expressly in FIG.1, each datacenter 130/140 may correspond with one or more datacenternetworks or domains, which may be domains other than the client domain.

Clients 112/114/122/124 and servers 132/13/142/144 may be configured toconnect to, or communicate via, a network 150. In some implementations,the clients 112/114 of a customer 110 may connect to the network 150 viaa communal connection point, link, or path 116. In some implementations,one or more clients 122/124 of a customer 120 may connect to, orcommunicate via, the network 150 using distinct connection points,links, or paths 126/128. A connection point, link, or path may be wired,as shown by links 116/126, wireless, as shown by connection point 128,or may include a combination of wired and wireless mediums.

The network 150 can, for example, be the Internet. In some embodiments,the network 150 may be, or include, a local area network (LAN), a widearea network (WAN), a virtual private network (VPN), or any other meansof electronic computer communication capable of transferring databetween any of clients 112/114/122/124 and servers 132/134/142/144. Thenetwork 150, the datacenters 130/140, or any other element, orcombination of elements, of the electronic computing and communicationsystem 100 may include network hardware such as routers, switches, loadbalancers, other network devices, or combinations thereof. For example,each of datacenters 130/140 may include one or more load balancers forrouting traffic from network 150 to various servers, such as servers132/134/142/144.

Other implementations of the electronic computing and communicationsystem may be used. For example, devices other than the clients112/114/122/124 and servers 132/134/142/144 shown may be included in theelectronic computing and communication system 100. In an implementation,one or more additional servers may operate as an electronic computingand communication system infrastructure control, from which servers,clients, or both, may be monitored, controlled, configured, or acombination thereof. For example, some or all of the techniquesdescribed herein may operate on the electronic computing andcommunication system servers.

In some embodiments, one or more of the elements of the electroniccomputing and communication system 100, such as the clients112/114/122/124 or the servers 132/134/142/144, may be configured tostore, manage, and provide one or more databases, tables, or otherinformation sources, or a portion thereof, such as a configurationmanagement database (CMDB), a management information base (MIB), or acombination thereof. A configuration management database may includerecords representing one or more entities, devices, or units of theelectronic computing and communication system, such as the clients112/114/122/124, the customers 110/120, the datacenters 130/140, theservers 132/134/142/144, the access point 128, the network 150, or anyother element, portion of an element, or combination of elements of theelectronic computing and communication system 100. The configurationmanagement database may include information describing theconfiguration, the role, or both, of an element of the electroniccomputing and communication system 100. In some embodiments, amanagement information base may include one or more databases listingcharacteristics of the elements of the electronic computing andcommunication system 100. In some embodiments, an object identifier(OID) may represent object identifiers of objects or elements in theMIB.

In some embodiments, the techniques and methods described herein,portions thereof, or combinations thereof, may be implemented on asingle device, such as a single server, or a combination of devices,such as a combination of clients 112/114/122/124 and servers132/134/142/144.

FIG. 2 is a block diagram of an example internal configuration of acomputing device 200, such as a client 112/114/122/124 or a server132/134/142/144 of the electronic computing and communication system 100shown in FIG. 1. As previously described, a client or server may be acomputing system including multiple computing devices, or a singlecomputing device, such as a mobile phone, a tablet computer, a laptopcomputer, a notebook computer, a desktop computer, a server computer, orthe like.

A computing device 200 can include components or units, such as aprocessor 210, memory 220, a network communication unit 230, a networkcommunication interface 240, a user interface 250, a sensor unit 260, apower source 270, a bus 280, or a combination thereof.

The processor 210 can be a central processing unit (CPU), such as amicroprocessor, and can include single or multiple processors, eachhaving single or multiple processing cores. The processor 210 caninclude single or multiple processors each having single or multipleprocessing cores. Alternatively, the processor 210 can include anothertype of device, or multiple devices, capable of manipulating orprocessing information now-existing or hereafter developed. For example,the processor 210 may include multiple processors interconnected in anymanner, including hardwired or networked, including wirelesslynetworked. In some embodiments, the operations of the processor 210 canbe distributed across multiple physical devices or units that can becoupled directly or across a local area or other network.

In some embodiments, the memory 220 may include volatile memory,non-volatile memory, or a combination thereof. For example, the memory220 may include volatile memory, such as one or more DRAM modules suchas DDR SDRAM, and non-volatile memory, such as a disk drive, a solidstate drive, flash memory, Phase-Change Memory (PCM), or any form ofnon-volatile memory capable of persistent electronic informationstorage, such as in the absence of an active power supply. In someembodiments, the memory 220 can include another type of device, ormultiple devices, capable of storing data or instructions for processingby the processor 210, now-existing or hereafter developed. The processor210 may access and manipulate data in the memory 220 via the bus 280.

The memory 220 can include executable instructions 222, data, such asapplication data 224, or a combination thereof, for immediate access bythe processor 210. The executable instructions 222 can include, forexample, an operating system and one or more application programs, whichmay be loaded or copied, in whole or in part, from non-volatile memoryto volatile memory to be executed by the processor 210. The executableinstructions 222 may be organized into programmable modules oralgorithms, functional programs, codes, code segments, or combinationsthereof, to perform various functions described herein. The operatingsystem can be, for example, Microsoft Windows®, Mac OS X®, Linux®, or anoperating system for a small device, such as a smart phone or tabletdevice, or a large device, such as a mainframe computer. Functionalprograms can include, for example, a web browser, a web server, adatabase server, or a combination thereof. The application data 224 caninclude, for example, user files, database catalogs, and configurationinformation. The memory 220 may include executable instructions 222,application data 224, or a combination thereof for implementing thetechniques described herein. The memory 220 may comprise one or multipledevices and may utilize one or more types of storage, such as solidstate or magnetic.

The network communication unit 240 can be coupled to the processor 210via the bus 280. In some embodiments, network communication unit 240 cancomprise one or more transceivers. The network communication unit 240can, for example, provide a connection or link to a network, such as thenetwork 150 shown in FIG. 1, via the network communication interface230, which may be a wired network interface, such as Ethernet, or awireless network interface (as shown). For example, the computing device200 may communicate with other devices via the network communicationunit 240 and the network interface 230 using one or more networkprotocols, such as Ethernet, TCP/IP, power line communication (PLC),WiFi, infrared, GPRS/GSM, CDMA, or the like.

A user interface 250 can include a display, a positional input device,such as a mouse, touchpad, touchscreen, or the like, a keyboard, or anyother human and machine interface devices. The user interface 250 can becoupled to the processor 210 via the bus 280. Other interface devicesthat permit a user to program or otherwise use the computing device 200can be provided in addition to or as an alternative to a display. Insome embodiments, the user interface 250 may include a display, whichmay be a liquid crystal display (LCD), a cathode-ray tube (CRT), a lightemitting diode (LED) display, such as an OLED display, or the like.

Although a single sensor 260 is shown, a computing device 200 maycontain any number of sensors and detectors 260, which may monitor thedevice 200 itself or the environment around the device 200. For example,a computing device 200 may contain a geospatial location identificationunit 260, such as a global positioning system (GPS) location unit. Insome embodiments, the power source 270 may be a battery, and thecomputing device 200 may operate independently of an external powerdistribution system. Any of the components of the computing device 200,such as the sensor 260 or the power source 270 may communicate with theprocessor 210 via the bus 280.

Other implementations of the internal architecture of clients andservers may be used. For example, a server may omit the location unit260. The operations of the processor 210 can be distributed acrossmultiple machines which can be coupled directly or across a local areaor other network. The memory 220 can be distributed across multiplemachines such as network-based memory or memory in multiple machinesperforming the operations of clients or servers. Although depicted hereas a single bus, the bus 280 can be composed of multiple buses, that maybe connected to each other through various bridges, controllers, and/oradapters.

FIG. 3 is a schematic of an example of an electronic computing andcommunication system for encrypting and decrypting partially encrypteddata using selective encryption delineation in accordance with thisdisclosure. The electronic computing and communication system 300 may besimilar to the electronic computing and communication system 100 shownin FIG. 1, except as described herein.

In some embodiments, the electronic computing and communication system300 can include customers, such as customers 310 and 320. A customer mayhave clients, such as clients 312, 314 for customer 310 and clients 322,324 for customer 320. The electronic computing and communication system300 can include datacenters 330/340, which may include servers332/334/342/344. Clients 312/314/322/324 and servers 332/13/342/344 maybe configured to connect to a network 350.

In some embodiments, the electronic computing and communication system300 may include a proxy 360, or gateway. The proxy 360 may be a deviceoperating on the communication path or paths between internal elements,such the clients 322/324, operating within the customer network ordomain 320, and external elements, such as the servers 332/334/342/344,operating outside the customer system 320. In some embodiments, thecommunication path between internal elements and external elements mayinclude one or more insecure portions, such as the Internet 350.

In some embodiments, the proxy 360 may be an edge encryption proxy, andmay include an encryption unit 362, a decryption unit 364, or both. Forexample, the proxy 360 may be an edge encryption proxy and may interceptcommunications between internal elements, such the clients 322/324,operating within the customer network or domain 320, and externalelements, such as the servers 332/334/342/344, operating outside thecustomer system 320. For simplicity and clarity, communications sentfrom internal elements, such the clients 322/324, to external elements,such as the servers 332/334/342/344, received or intercepted by theproxy 360 may be referred to herein as outbound data, outboundcommunications, outbound messages, or outbound information, andcommunications sent from external elements, such as the servers332/334/342/344, to internal elements, such the clients 322/324,received or intercepted by the proxy 360 may be referred to herein asinbound data, inbound communications, inbound messages, or inboundinformation. In some embodiments, the proxy 360 may relay, forward, orroute inbound communications, outbound communications, or both. In someembodiments, the proxy 360 may be transparent to the client 322/324.

In some embodiments, the proxy 360 may intercept outbound messages sentby internal elements, and may send corresponding communications toexternal elements on behalf of the internal elements, as shown in FIG.4. For example, a client, such the clients 322/324, may send a messageto a server, such as one of the servers 332/334/342/344, the proxy 360may intercept the outbound message, determine that the outbound messageinclude sensitive information, generate an encrypted, or partiallyencrypted, message corresponding to the outbound message, and send theencrypted, or partially encrypted, data to the server on behalf of theclient.

In some embodiments, the proxy 360 may intercept inbound messages sentby external elements, and may send corresponding communications tointernal elements, as shown in FIG. 5. For example, a server, such asone of the servers 332/334/342/344, may send a message to a client, suchthe clients 322/324, the proxy 360 may intercept the inbound message,determine that the inbound message include encrypted information,generate a decrypted message corresponding to the inbound message, andsend the decrypted data to the client.

For simplicity and clarity, outbound messages received at, orintercepted by, the proxy 360 are described herein as includingunencrypted data, such as clear text; however, the outbound messages mayinclude encrypted data. Similarly, data sent to internal elements, suchas the clients 322/324 by the proxy 360 are described herein asdecrypted data; however, the decrypted data may include data encryptedusing a technique other than selective encryption delineation.

For example, a client 322/324 may encrypt data using a first encryptionkey, to generate first encrypted data. The client 322/324 may sendoutbound data, including the first encrypted data, to one of the servers332/334/342/344. The proxy 360 may intercept and encrypt the outbounddata, or a portion thereof, which may include the first encrypted data,using a second encryption key, to generate second encrypted data. Theproxy 360 may send the output, which may include the second encrypteddata, to the server 332/334/342/344. Subsequently, the server332/334/342/344 may send inbound data, which may include the secondencrypted data, to the client 322/324. The proxy 360 may intercept theinbound data and may decrypt the second encrypted data to generate firstdecrypted data, which may include the first encrypted data. The proxy360 may send the first decrypted data to the client 322/324. The client322/324 may receive the first decrypted data, including the firstencrypted data, and may decrypt the first encrypted data to generatesecond decrypted data.

FIG. 4 is a diagram of an example of encrypting data using selectiveencryption delineation in accordance with this disclosure. In someembodiments, encrypting data using selective encryption delineation maybe implemented on a device, such as the proxy 310 shown in FIG. 3. Insome embodiments, encrypting data using selective encryption delineationmay include receiving data at 400, identifying insensitive data at 410,identifying sensitive data at 420, encrypting the sensitive data at 430,outputting the partially encrypted data at 440, or a combinationthereof.

In some embodiments, data may be received for encryption at 400. Forexample, a proxy device, such as the proxy 310 shown in FIG. 3, may be amember of, or operate within, a domain, such as the customer domain 320shown in FIG. 3, and may receive outbound data from a device in thedomain, such as a client 322/324 in the customer domain 320 as shown inFIG. 3. In some embodiments, the outbound data may include unencrypteddata, data encrypted via an external method, or a combination thereof.For simplicity and clarity, outbound data encrypted via an externalmethod may be considered to be unencrypted data herein, except asotherwise indicated. In some embodiments, the proxy device may be amember of, or operate within a network or domain other than the customerdomain. For example, a client device, which may be operating within thecustomer domain or another domain, may transmit outbound data to aserver, which may be outside the customer domain or within the customerdomain, and the request may be redirected, such as via a domain namesystem (DNS) redirect, to a proxy device, which may be operating outsidethe customer domain. In some embodiments, the proxy device may validatethe client device, such as via a log in process.

For example, the outbound data may include a request, such as aHypertext Transfer Protocol (HTTP) ‘GET’ request or an HTTP ‘POST’, to aserver outside the customer domain. The request may be intercepted bythe proxy, which may transmit a corresponding request includingencrypted, or partially encrypted, data to the server on behalf of theclient. For simplicity and clarity outbound data is described herein inthe context of HTTP GET or HTTP POST messages; however, other messagetypes, such as HTTP OPTIONS, HEAD, PUT, DELETE, or the like, may beused.

In some embodiments, the outbound data may include information organizedaccording to one or more protocols, such as Hypertext Markup Language(HTML, Extensible Markup Language (XML), JavaScript Object Notation(JSON), Simple Object Access Protocol (SOAP), or any other communicationprotocol or combination of communication protocols. For example, amessage from a client, in the customer domain, to a server, in anexternal domain, may include a Uniform Resource Locator (URL), such asthe following:

HTTP://www.example.com/path?param1=one&param2=two&protocol={“param3”.“three”;“param4”.“four”}.

-   -   [Example 1]

In Example 1, the first portion from the left “HTTP” may indicate aprotocol, such as the HTTP protocol. Although the examples herein usethe HTTP protocol, other protocols may be used, such as the FileTransfer Protocol (FTP), or the HTTP secure (HTTPS) protocol. The firstportion of the URL may be delineated from the second portion of the URLby a delimiter, such as “://”. The second portion of the URL,“www.example.com”, may indicate elements of a target domain, such as thetop-level domain “.com”, the domain “example”, and the subdomain “www”.The subdomain, domain, and top-level domain may each be delineated by adelimiter, such as a period “.”. The second portion of the URL may bedelineated from the third portion of the URL by the delimiter “/”. Thethird portion of the URL, “path” may indicate a location or path withinthe target domain. The third portion of the URL may be delineated fromthe fourth portion of the URL by a delimiter, such as the question mark“?”. In some embodiments, the portion of the URL to the right of the “?”delimiter may be referred to as the parameter string, or the parameters.The forth portion “?param1=one&param2=two&protocol={”param3”.”three”;“param4”.“four”}” may include multiple parameters, which may beformatted as name and value tuples. Individual parameters may bedelineated by a delimiter, such as the ampersand “&” or the semicolon“;”. The name and value of a tuple may be delineated by a delimiter,such as the equals sign “=”. For example, a first parameter in the URLincludes the “param1=one”, wherein the first portion of the parameter,“param1” indicates the name of the parameter, and the second portion“one” indicates the value of the parameter. In some embodiments, thevalue of a parameter may include information formatted according toanother protocol. For example, the fourth portion of the URL shownincludes the parameter “protocol={”param3”.“three”; “param4”.“four”}”,in which the first part, “protocol”, may include the name of the otherprotocol, such JSON or SOAP, and the second portion,“protocol={“param3”.”three”; “param4”.“four”}“, may include one or moreparameters in the corresponding protocol, such as ““param3”.”three””,and ““param4”.”four””.

Although an HTTP formatted URL is shown as an example herein, anycommunication format, syntax, or protocol may be used. In someembodiments, a message, such as an HTTP POST message may include aportion, such as a body portion or an entity body portion, which mayinclude an arbitrarily large amount of data. The data in the bodyportion may be formatted in accordance with respective syntax orprotocol corresponding to the type of data. The data stream may includea header portion, such as a “Content Type” header, prior to the bodyportion, which may indicate the type of data. Encoding and decoding ofthe body portion and corresponding headers may be similar to theencoding and decoding of a URL data stream as described herein.

In some embodiments, the outbound data received at 400, or portionsthereof, may be received as an array or stream of bytes.

In some embodiments, the outbound data received at 400 may be scanned at410. In some embodiments, the proxy may include an encryption unit,which may include a state machine, and scanning the outbound data mayinclude entering an unencrypted state in response to receiving theoutbound data.

In some embodiments, receiving the outbound data at 400 may includescanning the outbound data to identify sensitive portions. In someembodiments, the outbound data received at 400 may include sensitiveinformation, insensitive information, or a combination of sensitive andinsensitive information. For example, one or more of the portions of theoutbound data may be designated as insensitive. Insensitive data may bedata that may be transmitted outside the customer domain withoutencryption. For example, the outbound data may include an HTTP GETrequest that includes a URL that includes parameters as shown inEquation 1, and the name of one or more of the parameters, such as“param1” or “param2”, may be designated as insensitive and may betransmitted in an unencrypted form. In some embodiments, one or moreportion of the outbound data may be designated as sensitive. Sensitivedata may be data for which encryption is indicated prior to transmissionoutside the customer domain. For example, the outbound data may includean HTTP GET request that includes a URL that includes parameters asshown in Equation 1, and the value of the one or more of the parameters,such as “one” or “four”, may be designated as sensitive and may beencrypted prior to transmission.

In some embodiments, an insensitive portion may be identified at 410.For example, a first portion of the outbound data may be an insensitiveportion and may be identified at 410. In some embodiments, the proxy mayreceive the outbound data at 400, may enter an unencrypted state inresponse to receiving the outbound data, may determine that a firstportion of the outbound data does not include sensitive information, andmay include the corresponding portion of the outbound data in apartially encrypted output data stream, or an output buffer forsubsequent inclusion in the output data stream. For example, theoutbound data may include an HTTP GET request that includes a URL thatincludes parameters as shown in Equation 1, and a first portion of theoutbound data, such as “HTTP://www.example.com/path?param1=”, may beidentified as an insensitive portion.

In some embodiments, a sensitive portion may be identified at 420. Forexample, a second portion of the outbound data, subsequent to the firstportion, such as the value “one” shown in Example 1, may be a sensitiveportion and may be identified at 420. In some embodiments, the proxy, ora state machine of the proxy, may enter an encrypted state in responseto identifying the sensitive data at 420.

In some embodiments, the sensitive portion may be encrypted at 430. Insome embodiments, encrypting the sensitive portion at 430 may includedelineating the encrypted data at 432, generating encryption metadata at434, encrypting the sensitive data at 436, delineating an end of theencrypted data at 438, or a combination thereof.

In some embodiments, an encrypted portion delineator, such as anencryption sentinel, encrypted portion sentinel, may be output at 432.For example, an encryption sentinel may be included, subsequent to theinsensitive portion included at 420, in the partially encrypted outputdata stream, or the output buffer.

In some embodiments, the encryption sentinel may be a value or sequencesof values that cannot be otherwise included in, or is statisticallyunlikely to be otherwise included in, the data stream. For example, insome embodiments, an encryption sentinel may be implemented as a longarbitrary collection of characters, the length and composition of whichmake it very unlikely that such a sequence would otherwise appear in thedata stream in encrypted, unencrypted, or partially encrypted, form. Inorder to ensure that it is very unlikely that such a sequence wouldotherwise appear in the data stream, such a sequence may be relativelylong, such as a sequence including twenty or more characters.

In some embodiments, an encryption sentinel may be implemented as adefined value that does not otherwise appear in the data stream, such asa Unicode private character or non-character. For example, the datastream, in encrypted, unencrypted, or partially encrypted form, mayinclude characters encoded according to a defined encoding scheme, suchas the Unicode character encoding standard, and the beginning of anencrypted portion may be delineated using a non-character encryptedportion sentinel, which may be a valid code in the defined encodingscheme. In an example, the non-character encrypted portion sentinel maybe “\uFDD0\uFDD1”.

In some embodiments, encrypting the sensitive information at 430 mayinclude generating one or more parameters, or fields, describing theencrypted data, which may be referred to herein as encryption metadata,at 434. In some embodiments, the encryption metadata may be output asunencrypted data. The encryption metadata may, for example, includeinformation for use in decrypting the encrypted data, such as anorder-preserving token, an identification of an encryption algorithmused for encrypting the encrypted data, a symbolic name or alias thatidentifies an encryption key for encrypting or decrypting the encrypteddata, or the like. Each metadata parameter, field, or element may bedelimited using a respective defined encryption metadata start sentineland a corresponding defined encryption metadata end sentinel. Theencryption metadata start and end sentinels may be a private, ornon-character, Unicode values, or a respective sequences thereof. Insome embodiments, the encrypted data may be included, subsequent to theencryption metadata, in the partially encrypted output data stream, oroutput buffer.

In some embodiments, one or more portions of sensitive informationidentified at 420, may be encrypted at 436. In some embodiments,encrypting the sensitive information at 436 may include outputtingencrypted data. For example, the encrypted data may be included,subsequent to the encrypted portion sentinel included at 432 and theencryption metadata included at 434, in the partially encrypted outputdata stream, or output buffer.

In some embodiments, encrypting the unencrypted outbound sensitive datamay include using an encryption cipher to generate binary data. In someembodiments, the binary data may be base 64-encoded, which may produce asequence of valid characters, such as Unicode characters, which mayvalidly appear in, for example, a web page or in database, such as in aCHAR or VARCHAR type field.

In some embodiments, an end encrypted portion delineator, such as an endencryption sentinel, or end encrypted portion sentinel, may be output at438. For example, an end encryption sentinel may be included, subsequentto the encrypted data included at 436, in the partially encrypted outputdata stream, or the output buffer.

In some embodiments, the end encryption sentinel may be a value orsequences of values that cannot be otherwise included in, or isstatistically unlikely to be otherwise included in, the data stream. Forexample, in some embodiments, an end encryption sentinel may beimplemented as a long arbitrary collection of characters, the length andcomposition of which make it very unlikely that such a sequence wouldotherwise appear in the data stream in encrypted, unencrypted, orpartially encrypted, form. In order to ensure that it is very unlikelythat such a sequence would otherwise appear in the data stream, such asequence may be relatively long, such as a sequence including twenty ormore characters.

In some embodiments, an end encryption sentinel may be implemented as adefined value that does not otherwise appear in the data stream, such asa Unicode private character or non-character. For example, the datastream, in encrypted, unencrypted, or partially encrypted form, mayinclude characters encoded according the Unicode character encodingstandard, and the end of an encrypted portion may be delineated using anon-character end encrypted portion sentinel. In an example, thenon-character end encrypted portion sentinel may be “\uFDEE\uFDEF”.

In some embodiments, the proxy, or a state machine thereof, may enter anunencrypted state in response to outputting the end encrypted portionsentinel at 438. In some embodiments, the outbound data received at 400may include insensitive data, sensitive data, or a combination thereofsubsequent to the sensitive data encrypted at 430, and identifyinginsensitive data at 410, identifying sensitive data at 420, encryptingthe sensitive data at 430, may be repeated for the subsequent data asindicated by the broken line in FIG. 4.

In some embodiments, partially encrypted data corresponding to theoutbound data received at 400 may be output at 440. For example, thepartially encrypted output data stream, or the content of the outputbuffer, may be stored in memory or transmitted to an external device,such as a sever in another domain. For example, the outbound datareceived at 400 may include an HTTP GET request, or an HTTP POST, whichmay include a combination of insensitive and sensitive data inunencrypted form, and addressed to a server outside the customer domain,the proxy may generate partially encrypted data corresponding to theoutbound data, which be an HTTP GET request, or an HTTP POST, and whichmay include a combination of unencrypted insensitive data and encryptedsensitive data, and the proxy may transmit the partially encrypted datato the server.

FIG. 5 is a diagram of an example of decrypting partially encrypted datausing selective encryption delineation in accordance with thisdisclosure. In some embodiments, decrypting partially encrypted datausing selective encryption delineation may be implemented on a device,such as the proxy 310 shown in FIG. 3. In some embodiments, decryptingpartially encrypted data using selective encryption delineation mayinclude receiving the partially encrypted data at 500, identifying anunencrypted portion at 510, identifying an encrypted portion sentinel at520, decrypting an encrypted portion at 530, outputting decrypted dataat 540, or a combination thereof.

In some embodiments, partially encrypted data may be received at 500.For example, a proxy device, such as the proxy 310 shown in FIG. 3, maybe a member of, or operate within, a domain, such as the customer domain120 shown in FIG. 3, and may receive partially encrypted data, such asan HTTP response, from a device in a remote domain, which may be adomain other than the customer domain, such as a server 132/134 in adomain corresponding to the datacenter 130 as shown in FIG. 3, on behalfof a client, such as the client 322/324 shown in FIG. 3.

For simplicity and clarity, encrypted, or partially encrypted, datareceived by the proxy from an external device may be referred to hereinas inbound data. In some embodiments, the inbound data may includeunencrypted data, data encrypted using selective encryption delineation,or a combination thereof. For simplicity and clarity, inbound data, suchas an HTTP response, that includes a mixture of unencrypted andencrypted data may be referred to herein as a partially, or selectively,encrypted string, a partially, or selectively, encrypted message, orpartially, or selectively, encrypted data.

Although an HTTP formatted response is described as an example herein,any communication format, syntax, or protocol may be used. In someembodiments, a message, such as an HTTP response message may include aportion, such as a body portion or an entity body portion, which mayinclude an arbitrarily large amount of data. The data in the bodyportion may be formatted in accordance with respective syntax orprotocol corresponding to the type of data. The data stream may includea header portion, such as a “Content Type” header, prior to the bodyportion, which may indicate the type of data. Encoding and decoding ofthe body portion and corresponding headers may be similar to theencoding and decoding of a URL data stream as described herein. In someembodiments, the inbound data may include information organizedaccording to one or more protocols, such as Hypertext Markup Language(HTML, Extensible Markup Language (XML), JavaScript Object Notation(JSON), Simple Object Access Protocol (SOAP), or any other communicationprotocol or combination of communication protocols.

In some embodiments, the inbound data received by the proxy at 500 maybe received in response to transmitting outbound data, such as thetransmitting shown at 440 in FIG. 4. For example, a client in thecustomer domain may transmit a message, such as a Hypertext TransferProtocol (HTTP) ‘GET’ request or a HTTP ‘POST’, to a server outside thecustomer domain. The message may be intercepted by the proxy, which maytransmit a corresponding encrypted, or partially encrypted, message tothe server on behalf of the client. The server may send a response, suchas a web page, to the proxy. The response may include encrypted, orpartially encrypted, data, the proxy may decrypt the inbound data, maysend the decrypted response to the client. Although not expresslydescribed herein, other message types, such as HTTP OPTIONS, HEAD, PUT,DELETE, or the like, may be used.

In some embodiments, receiving the inbound at 500 may include scanningthe partially encrypted data. For example, in some embodiments, theinbound data, or portions thereof, may be received as an array or streamof bytes, and the proxy may byte-wise scan the incoming partiallyencrypted data stream. In some embodiments, scanning the partiallyencrypted data at 500 may include parsing the partially encrypted datato identify encrypted portions. In some embodiments, the proxy mayinclude a decryption unit, which may include a state machine, andscanning the partially encrypted data may include entering anunencrypted state in response to receiving the partially encrypted data.In some embodiments, scanning the partially encrypted data at 500 mayinclude sequentially evaluating each byte of the partially encrypteddata, to determine whether the byte of partially encrypted data includesan encrypted portion sentinel.

In some embodiments, scanning, or parsing, the inbound data at 500 mayinclude scanning, or parsing, the inbound data using selectiveencryption delineation, and may omit parsing the inbound data streamaccording to other defined stream protocol or protocols. For example,the inbound data may include may include information organized accordingto one or more protocols, such as HTTP formatted data, HTML formatteddata, XML formatted data, or the like, data encrypted using anencryption protocol other than selective encryption delineation, or acombination of protocols or formats other than selective encryptiondelineation, and scanning, or parsing, the inbound data may omitscanning, parsing, or otherwise interpreting, one or more portions ofthe inbound data according to the other protocols. In some embodiments,in conjunction with the cryptographic functions of the proxy describedherein, the proxy may scan, parse, evaluate, or interpret one or moreportions of the inbound data organized, or formatted, using a protocolother than selective encryption delineation for routing the inbounddata, such as to identify a source, a destination, or the like, for theinbound data.

In some embodiments, an unencrypted portion may be identified at 510.For example, a first portion of the partially encrypted data may be anunencrypted portion and may be identified at 510. In some embodiments,the proxy may enter an unencrypted state in response to receiving thepartially encrypted data at 500, may evaluate a byte of the partiallyencrypted data, may determine that the byte does not include anencrypted portion sentinel, and may include the byte in an outputdecrypted data stream, or an output buffer for subsequent inclusion inthe output decrypted data stream. Although the portion of the partiallyencrypted data preceding an encrypted portion sentinel is describedherein as unencrypted data, the data may include data encrypted using atechnique other than selective encryption delineation.

In some embodiments, an encrypted portion sentinel may be identified at520. For example, the proxy may evaluate a byte of the partiallyencrypted data, which may be subsequent to the unencrypted portionidentified at 510, and the proxy may determine that the byte includes anencrypted portion delimiter, encryption sentinel, or encrypted portionsentinel. In some embodiments, an encryption sentinel may be a value, orsequences of values, that cannot be otherwise included in, or isstatistically unlikely to be otherwise included in, the data stream. Forexample, in some embodiments, an encryption sentinel may be implementedas a long arbitrary collection of characters, as described herein. Inanother example, an encryption sentinel may be implemented as a definedvalue that does not otherwise appear in the data stream, such as aUnicode private character or non-character as described herein. In someembodiments, the encrypted portion sentinel may be omitted from thedecrypted output.

In some embodiments, the proxy may decrypt the encrypted portion of theinbound data, which may be the data subsequent to the encrypted portionsentinel in the inbound data, at 530. For example, the proxy may enteran encrypted state in response to identifying the encrypted portionsentinel at 520, and may begin processing the inbound data stream asencrypted data.

In some embodiments, decrypting the encrypted portion of the inbounddata at 530 may include identifying encryption metadata. The encryptionmetadata may, for example, include information for use in decrypting theencrypted data, such as an order-preserving token, an identification ofan encryption algorithm used for encrypting the encrypted data, asymbolic name or alias that identifies an encryption key for encryptingor decrypting the encrypted data, or the like. Each metadata parameter,field, or element may be delimited using a respective defined encryptionmetadata start sentinel and a corresponding defined encryption metadataend sentinel.

In some embodiments, the proxy may byte-wise process the encrypted data,and may identify an encryption metadata sentinel in the encryptedportion of the inbound data. For example, the proxy may evaluate a byteof the encrypted portion of the inbound data, which may be subsequent tothe encrypted portion sentinel in the inbound data, and the proxy maydetermine that the byte includes an encryption metadata sentinel. Insome embodiments, the proxy may identify encryption metadata subsequentto the encryption metadata sentinel. In some embodiments, the encryptionmetadata may be unencrypted data. In some embodiments, the proxy mayidentify an end encryption metadata sentinel subsequent to theencryption metadata sentinel. In some embodiments, the encryptionmetadata may be omitted from the decrypted output.

In some embodiments, decrypting the encrypted portion of the inbounddata at 530 may include identifying encrypted data, such as base-64coded encrypted data, subsequent to the end encryption metadatasentinel. In some embodiments, the encrypted portion of the inbound datamay omit encryption metadata, and the encrypted data may be identifiedsubsequent to the encrypted portion sentinel.

In some embodiments, decrypting the encrypted portion of the inbounddata at 530 may include decrypting the encrypted data. In someembodiments, the encrypted data, which may be included in the encryptedportion subsequent to the metadata, may be binary data produced by anencryption cipher, and may be base 64-encoded, which may produce asequence of valid characters, such as Unicode characters, which mayvalidly appear in, for example, a web page or in database, such as in aCHAR or VARCHAR type field. In some embodiments, a decryption unit atthe proxy, may generate decrypted data by applying a cryptographicfunction to the encrypted data using a decryption key. In someembodiments, cryptographic function, the decryption key, or both, may bedefined values or may be identified based on the encryption metadata. Insome embodiments, the decrypted data may be included in the outputdecrypted data stream, or an output buffer for subsequent inclusion inthe output decrypted data stream.

In some embodiments, decrypting the encrypted portion of the inbounddata at 530 may include identifying an end encrypted portion sentinel inthe inbound data. For example, the proxy may evaluate a byte of theencrypted portion of the inbound data, which may be subsequent to theencrypted metadata, and the proxy may determine whether the byteincludes an end encryption sentinel. In some embodiments, the byte mayomit an end encrypted portion sentinel and the proxy may decrypt thebyte as indicated above. In some embodiments, the byte may include anend encrypted portion sentinel and the proxy may enter an unencryptedstate in response to identifying the end encrypted portion sentinel. Insome embodiments, the end encrypted portion sentinel may be omitted fromthe decrypted output. In some embodiments, the inbound data received at500 may include unencrypted data, encrypted data, or a combinationthereof subsequent to the data decrypted at 530, and identifyingunencrypted data at 510, identifying encrypted portion sentinels at 520,decrypting data at 530, or a combination thereof, may be repeated forthe subsequent data as indicated by the broken line in FIG. 5.

In some embodiments, decrypted data corresponding to the inbound datareceived at 500 may be output at 540. For example, the decrypted outputdata stream, or the content of the output buffer, may be stored inmemory or transmitted to an internal device, such as a client device inthe customer domain.

In an example, a client in the customer domain may transmit outbounddata, such as an HTTP GET request, or an HTTP POST, which may includeinsensitive data, sensitive data, or a combination thereof, inunencrypted form, to an external device, such as a server in anotherdomain. The proxy may intercept the request and may generate partiallyencrypted data corresponding to the outbound data as shown in FIG. 4,and the proxy may transmit the partially encrypted data to the server.In some embodiments, the outbound data received by the proxy may omitsensitive data, and the proxy may send the request to the server inunencrypted form. The unencrypted data, or partially encrypted data sentby the proxy to the external server may be an HTTP GET request, or anHTTP POST, and may include unencrypted insensitive data, encryptedsensitive data, or a combination thereof. In response to the request,the server may send a response to the client, which may includepartially encrypted data. The proxy may intercept the response, orotherwise receive the partially encrypted data on behalf of the client,may decrypt the encrypted data, may generate a decrypted output datastream, and may send the decrypted output data stream to the client.

FIG. 6 is a diagram of an example of managing data encrypted usingselective encryption delineation in accordance with this disclosure. Insome embodiments, managing data encrypted using selective encryptiondelineation may be implemented on a device, such as the server332/334/342/344 shown in FIG. 3. In some embodiments, managing dataencrypted using selective encryption delineation may include receivingpartially encrypted data at 600, identifying an unencrypted portion at610, identifying an encrypted portion at 620, storing data at 630,receiving a request for partially encrypted data at 640, outputting aresponse including partially encrypted data at 650, or a combinationthereof.

In some embodiments, partially encrypted data may be received at 600.For example, a server, such as the server 332/334/342/344 shown in FIG.3, which may be in a domain other than a customer domain, such as thecustomer domain 320 shown in FIG. 3, may receive partially encrypteddata from a proxy, such as the proxy 360 shown in FIG. 3, which may bein the customer domain, on behalf of a client, such as the client322/324 shown in FIG. 3, which may be in the customer domain. In someembodiments, the partially encrypted data may include unencrypted data,encrypted data, or a combination thereof. In some embodiments, theencrypted data may be generated using selective encryption delineation.For example, the proxy may generate the partially encrypted data asshown in FIG. 4.

In some embodiments, an unencrypted portion may be identified at 610.For example, in some embodiments, the partially encrypted data, orportions thereof, may be received as an array or stream of bytes, andthe server may byte-wise scan the partially encrypted data stream. Insome embodiments, scanning the partially encrypted data may includeparsing the partially encrypted data. In some embodiments, scanning thepartially encrypted data may include sequentially evaluating each byteof the partially encrypted data, to determine whether the byte ofpartially encrypted data includes an encrypted portion sentinel. In someembodiments, a first portion of the partially encrypted data, which mayinclude one or more bytes, may omit an encrypted portion sentinel, andmay be identified as unencrypted data. For example, the partiallyencrypted data may correspond with Example 1, and the first portion mayinclude unencrypted data corresponding to“HTTP://www.example.com/path?param1=”. Although the first portion isdescribed as unencrypted data, the unencrypted data, or a portionthereof, may include encrypted data generated using an encryptiontechnique other than selective encryption delineation, and the servermay decrypt the data to identify the unencrypted data.

In some embodiments, an encrypted portion may be identified at 620. Forexample, the server may determine that the received partially encrypteddata includes an encrypted portion sentinel and a subsequent endencrypted portion sentinel, and may identify a portion of the partiallyencrypted data beginning at the encrypted portion sentinel, orimmediately subsequent to the encrypted portion sentinel, and ending atthe end encrypted portion sentinel, or immediately prior to the endencrypted portion sentinel, as a selectively encrypted portion. In someembodiments, the server may byte-wise scan the partially encrypted datastream to identify the encrypted portion sentinel, the end encryptedportion sentinel, or both.

In an example, partially encrypted data based on Example 1 may include afirst unencrypted portion, such as“HTTP://www.example.com/path?param1=”, followed by a first encryptedportion sentinel, followed by a first encrypted portion, which mayinclude an encrypted representation of the value “one” as shown inExample 1, followed by a first end encrypted portion sentinel, followedby a second unencrypted portion, such as “&param2=”, followed by asecond encrypted portion sentinel, followed by a second encryptedportion, which may include an encrypted representation of the value“two” as shown in Example 1, followed by a second end encrypted portionsentinel, followed by a third unencrypted portion, such as “&protocol=”,followed by a third encrypted portion sentinel, followed by a thirdencrypted portion, which may include an encrypted representation of“{“param3”.”three”; “param4”.”four”}” as shown in Example 1, followed bya third end encrypted portion sentinel.

In some embodiments, the partially encrypted data may include encryptionmetadata associated with encrypted data. For example, the partiallyencrypted data may include encryption metadata subsequent to anencrypted portion sentinel and prior to a corresponding encryptedportion. In some embodiments, the server may scan the selectivelyencrypted portion and may identify an encryption metadata startsentinel, followed by some data, followed by a corresponding encryptionmetadata end sentinel, and may identify the data subsequent to theencryption metadata start sentinel and prior to the correspondingencryption metadata end sentinel as encryption metadata.

In some embodiments, the partially encrypted data may be stored at 630.For example, the partially encrypted data may be stored in a datastorage unit, such as a database, associated with the server. In someembodiments, storing the partially encrypted data at 630 may includedetermining a data storage location, such as a databased, table, column,or field to store the partially encrypted data, or a portion thereof. Insome embodiments, a data storage location may be identified based on theunencrypted data identified at 610. For example, a field in a databasemay be identified based on the first unencrypted portion“HTTP://www.example.com/path?param1=”.

In some embodiments, storing the partially encrypted data at 630 mayinclude storing encrypted data, such as the encrypted portion identifiedat 620 in an identified data storage location. For example, a datastorage location, such as a field in a database, may be identified basedon the first unencrypted portion, “HTTP://www.example.com/path?param1=”,identified at 610, and the encrypted data identified at 620, subsequentto the first unencrypted portion, may be stored at the identified datastorage location. In some embodiments, storing the encrypted data mayomit decrypting the encrypted data. For example, decryption information,such as decryption keys, for decrypting the encrypted data may beinaccessible to the server, such that the server may be effectivelyincapable of decrypting the encrypted data, and the encrypted data maybe stored in encrypted form. In some embodiments, storing the encrypteddata may include storing the encrypted portion sentinel, the endencrypted portion sentinel, or both, with the encrypted data. In someembodiments, storing the encrypted data may omit storing the encryptedportion sentinel, the end encrypted portion sentinel, or both.

In some embodiments, the partially encrypted data may include encryptionmetadata associated with encrypted data, and storing the partiallyencrypted data at 630 may include storing the encryption metadata inassociation with the corresponding encrypted data.

In some embodiments, the partially encrypted data received at 600 mayinclude unencrypted data, encrypted data, or a combination thereof,subsequent to the end encrypted portion sentinel identified at 620, andidentifying an unencrypted portion at 610, identifying an encryptedportion at 620, storing data at 630, or a combination thereof, may berepeated for the subsequent data as indicated by the broken line in FIG.6.

In some embodiments, a request for partially encrypted data may bereceived at 640. For example, a client, such as the client 322/324 shownin FIG. 3, which may be in a customer domain, such as the customerdomain 320 shown in FIG. 3, may send a request, such as an HTTP GETrequest, to a server, such as the server 332/334/342/344 shown in FIG.3, which may be in a domain other than the customer domain, the requestmay be intercepted by a proxy, such as the proxy 360 shown in FIG. 3,which may be in the customer domain, and the proxy may send acorresponding request to the sever on behalf of the client.

In some embodiments, output may be generated at 650 in response toreceiving the request at 640. For example, a server, such as one or moreof the servers 332/334/342/344 shown in FIG. 3, may generate a partiallyencrypted data stream and may transmit the partially encrypted datastream to the client via the proxy. In some embodiments, generating thepartially encrypted data stream may include encrypting one or moreportions of the data stream and including the encrypted portions in theoutput data stream. For example, the server may encrypt data such thatdecryption information for decrypting the encrypted data is unavailableto the server. In some embodiments, generating the partially encrypteddata stream may include identifying one or more previously encryptedportions, such as the encrypted portion stored at 630, and including thepreviously encrypted portion or portions in the output data stream.

In some embodiments, including the encrypted data in the output datastream may include including an encrypted portion sentinel in the outputdata stream, including encryption metadata in the output data streamsubsequent to the encrypted portion sentinel, base-64 encoding theencrypted data, including the base-64 encoded encrypted data in theoutput data stream subsequent to the encrypted portion sentinel, or theencryption metadata, including an end encrypted portion sentinel in theoutput data stream subsequent to the encrypted data, or a combinationthereof. Other encrypted and unencrypted data may be similarly includedin subsequent portions of the partially encrypted output data stream.

The implementations of the electronic computing and communicationsystem, including clients 112/114/122/124 and servers 132/134/142/144(and the algorithms, methods, instructions, etc. stored thereon and/orexecuted thereby), can be realized in hardware, software, or anycombination thereof. The hardware can include, for example, computers,intellectual property (IP) cores, application-specific integratedcircuits (ASIC s), programmable logic arrays, optical processors,programmable logic controllers, microcontrollers, servers,microprocessors, digital signal processors or any other suitablecircuit. In the claims, the term “processor” should be understood asencompassing any of the foregoing hardware, either singly or incombination. The terms “signal” and “data” are used interchangeably.Further, portions of clients 112/114/122/124 and servers 132/134/142/144are not necessarily implemented in the same manner.

Further, in an embodiment, for example, clients 112/114/122/124, proxy310, and servers 132/134/142/144 can be implemented using a specialpurpose computer/processor, which can contain specialized hardware forcarrying out any of the methods, algorithms, or instructions describedherein.

Further, all or a portion of embodiments of the present invention can beimplemented using a special purpose computer/processor with a computerprogram that, when executed, carries out any of the respectivetechniques, algorithms and/or instructions described herein, and whichcan contain specialized hardware for carrying out any of the techniques,algorithms, or instructions described herein.

Implementations or portions of implementations of the above disclosurescan take the form of a computer program product accessible from, forexample, a computer-usable or computer-readable medium. Acomputer-usable or computer-readable medium can be any device that can,for example, tangibly contain, store, communicate, or transport aprogram or data structure for use by or in connection with anyprocessor. The medium can be, for example, an electronic, magnetic,optical, electromagnetic, or a semiconductor device. Other suitablemediums are also available. Such computer-usable or computer-readablemedia can be referred to as non-transitory memory or media, and mayinclude RAM or other volatile memory or storage devices that may changeover time.

As used herein, the terminology “determine” and “identify”, or anyvariations thereof, includes selecting, ascertaining, computing, lookingup, receiving, determining, establishing, obtaining, or otherwiseidentifying or determining in any manner whatsoever using one or more ofthe devices shown and described herein. As used herein, the terminology“generating”, or any variations thereof, includes combining,calculating, computing, aggregating, rendering, laying out, drawing, orotherwise producing in any manner whatsoever using one or more of thedevices shown and described herein. As used herein, the terminology“automatic”, “automatically”, “automated”, or any variation thereof,including use of the prefix “auto-”, includes initiating or executing byone or more of the devices shown and described herein without humanintervention. As used herein, the terminology “cardinality” includes anumber or count of elements or items in a set, group, plurality, or anyother collection of zero or more elements. As used herein, theterminology “receiving” includes receiving via a network, retrievingfrom memory, or otherwise ascertaining the identified information.

The above-described embodiments have been described in order to alloweasy understanding of the present invention and do not limit the presentinvention. On the contrary, the invention is intended to cover variousmodifications and equivalent arrangements included within the scope ofthe appended claims, which scope is to be accorded the broadestinterpretation so as to encompass all such modifications and equivalentstructure as is permitted under the law.

What is claimed is:
 1. A method of decrypting a partially encrypted datastream, the method comprising: receiving, from a remote server in afirst network domain, at an edge encryption proxy in a second networkdomain, a partially encrypted data stream; scanning the partiallyencrypted data stream, wherein scanning the partially encrypted datastream includes: identifying a first portion of the partially encrypteddata stream, wherein the first portion omits an encrypted portionsentinel, including the first portion in a decrypted output data stream,identifying an encrypted portion sentinel in the partially encrypteddata stream subsequent to the first portion, identifying an encryptedportion in the partially encrypted data stream subsequent to theencrypted portion sentinel, generating a decrypted data portion bydecrypting the encrypted portion, wherein decrypting the encryptedportion includes: identifying an encrypted data portion in the encryptedportion, the encrypted data portion omitting an end encrypted portionsentinel; decrypting the encrypted data portion; and identifying an endencrypted portion sentinel in the encrypted portion subsequent to theencrypted data portion, including the decrypted data portion in thedecrypted output data stream; and outputting the decrypted output datastream to a client device in the second network domain.
 2. The method ofclaim 1, wherein scanning the partially encrypted data stream includesbyte-wise scanning.
 3. The method of claim 1, wherein the first portionincludes unencrypted data.
 4. The method of claim 1, wherein thepartially encrypted data stream includes data encoded in accordance witha defined encoding scheme.
 5. The method of claim 4, wherein the definedencoding scheme is a Unicode encoding scheme.
 6. The method of claim 4,wherein: the encrypted portion sentinel is a valid code in the definedencoding scheme; the end encrypted portion sentinel is a valid code inthe defined encoding scheme that differs from the encrypted portionsentinel; the first portion includes codes that are valid in the definedencoding scheme and omits codes other than codes that are valid in thedefined encoding scheme; and the encrypted portion includes codes thatare valid in the defined encoding scheme, omits codes other than codesthat are valid in the defined encoding scheme, and omits the encryptedportion sentinel.
 7. The method of claim 1, wherein decrypting theencrypted portion includes: identifying encryption metadata in theencrypted portion by: identifying an encryption metadata start sentinelin the encrypted portion; identifying the encryption metadata in theencrypted portion subsequent to the encryption metadata start sentinel,wherein the encryption metadata omits the encryption metadata startsentinel, and omits an encryption metadata end sentinel; and identifyingthe encryption metadata end sentinel in the encrypted portion subsequentto the encryption metadata; and omitting the encryption metadata startsentinel, the encryption metadata, and the encryption metadata endsentinel from the encrypted data portion.
 8. The method of claim 1,wherein decrypting the encrypted data portion includes decrypting theencrypted data portion using decryption information that is unavailableto the remote server.
 9. A method of delineating an encrypted portion ofa selectively encrypted data stream, the method comprising: generating apartially encrypted data stream, wherein generating the partiallyencrypted data stream includes: identifying an unencrypted input dataportion, including the unencrypted input data portion in the partiallyencrypted data stream, identifying an encrypted input data portion,including an encrypted portion sentinel in the partially encrypted datastream subsequent to the unencrypted input data portion, including theencrypted input data portion in the partially encrypted data streamsubsequent to the encrypted portion sentinel, and including an endencrypted portion sentinel in the partially encrypted data streamsubsequent to the encrypted input data portion; and outputting thepartially encrypted data stream.
 10. The method of claim 9, wherein thepartially encrypted data stream includes data encoded in accordance witha defined encoding scheme.
 11. The method of claim 10, wherein thedefined encoding scheme is a Unicode encoding scheme.
 12. The method ofclaim 10, wherein: the encrypted portion sentinel is a valid code in thedefined encoding scheme; the end encrypted portion sentinel is a validcode in the defined encoding scheme that differs from the encryptedportion sentinel; including the unencrypted input data portion in thepartially encrypted data stream includes including the unencrypted inputdata portion in the partially encrypted data stream as a first partiallyencrypted data stream portion, such that: the first partially encrypteddata stream portion includes codes that are valid in the definedencoding scheme, the first partially encrypted data stream portion omitscodes other than codes that are valid in the defined encoding scheme,the first partially encrypted data stream portion omits the encryptedportion sentinel, and the first partially encrypted data stream portionomits the end encrypted portion sentinel; and the encrypted portionincludes codes that are valid in the defined encoding scheme, omitscodes other than codes that are valid in the defined encoding scheme,omits the encrypted portion sentinel, and omits the end encryptedportion sentinel.
 13. The method of claim 9, wherein identifying theencrypted input data portion includes identifying encryption metadata,and wherein including the encrypted input data portion in the partiallyencrypted data stream includes: including an encryption metadata startsentinel in the in the partially encrypted data stream; including theencryption metadata in the in the partially encrypted data streamsubsequent to the encryption metadata start sentinel, wherein theencryption metadata omits the encryption metadata start sentinel, andomits an encryption metadata end sentinel; and including the encryptionmetadata end sentinel in the in the partially encrypted data streamsubsequent to the encryption metadata.
 14. The method of claim 9,wherein generating the partially encrypted data stream includesgenerating the partially encrypted data stream by a server in a firstnetwork domain, outputting the partially encrypted data stream includestransmitting the partially encrypted data stream to an edge encryptionproxy in a second network domain, and wherein the encrypted input dataportion is encrypted such that decryption information for decrypting theencrypted input data portion is unavailable to the server and isavailable to the edge encryption proxy.
 15. A non-transitorycomputer-readable storage medium, comprising executable instructionsthat, when executed by a processor, facilitate performance ofoperations, comprising: receiving, at an edge encryption proxy in afirst network domain, from a client device in the first network domain,a first request for information, the first request indicating a remoteserver in a second network domain; transmitting a second request for theinformation to the remote server on behalf of the client device; inresponse to transmitting the second request to the remote server,receiving, from the remote server, at the edge encryption proxy, apartially encrypted data stream; including a first portion of thepartially encrypted data stream in a decrypted output data stream,wherein the first portion omits an encrypted portion sentinel;identifying an encrypted portion in the partially encrypted data streamsubsequent to an encrypted portion sentinel in the partially encrypteddata stream, the encrypted portion sentinel subsequent to the firstportion in the partially encrypted data stream; generating a decrypteddata portion by decrypting the encrypted portion, wherein decrypting theencrypted portion includes: generating the decrypted data portion bydecrypting an encrypted data portion from the encrypted portion, suchthat the decrypted data portion includes at least a portion of theinformation, the encrypted data portion omitting an end encryptedportion sentinel; and identifying the end encrypted portion sentinel inthe encrypted portion subsequent to the encrypted data portion;including the decrypted data portion in the decrypted output datastream; and outputting the decrypted output data stream to the clientdevice as a response to the first request.
 16. The non-transitorycomputer-readable storage medium of claim 15, wherein the first portionincludes unencrypted data.
 17. The non-transitory computer-readablestorage medium of claim 15, wherein the partially encrypted data streamincludes data encoded in accordance with a defined encoding scheme. 18.The non-transitory computer-readable storage medium of claim 17, whereinthe defined encoding scheme is a Unicode encoding scheme.
 19. Thenon-transitory computer-readable storage medium of claim 17, wherein:the encrypted portion sentinel is a valid code in the defined encodingscheme; the end encrypted portion sentinel is a valid code in thedefined encoding scheme that differs from the encrypted portionsentinel; the first portion includes codes that are valid in the definedencoding scheme and omits codes other than codes that are valid in thedefined encoding scheme; and the encrypted portion includes codes thatare valid in the defined encoding scheme, omits codes other than codesthat are valid in the defined encoding scheme, and omits the encryptedportion sentinel.
 20. The non-transitory computer-readable storagemedium of claim 15, wherein decrypting the encrypted portion includes:identifying encryption metadata in the encrypted portion by: identifyingan encryption metadata start sentinel in the encrypted portion;identifying the encryption metadata in the encrypted portion subsequentto the encryption metadata start sentinel, wherein the encryptionmetadata omits the encryption metadata start sentinel, and omits anencryption metadata end sentinel; identifying the encryption metadataend sentinel in the encrypted portion subsequent to the encryptionmetadata; and omitting the encryption metadata start sentinel, theencryption metadata, and the encryption metadata end sentinel from theencrypted data portion.